Problem

The auto-detection strategy to find a lute executable on the user's system is currently shallow and hard-coded.

It:

• looks for lute in the foreman bin (workspace-dependent)
• if not found, looks for a hard-coded (and outdated) lute version in rokit tool storage (horrible)
• falls back to system path

Solution

Use a more exhaustive strategy to find existing lute paths:

• check foreman / rokit bin, if found use that executable
• fallback to foreman / rokit tool storage, picking latest lute version (if any)
• finally, fall back to system path

We also confirm that the found paths are actually executable, since foreman/rokit bins can be stale.

There are still some issues with this, for example, the fact that our first check is in the foreman/rokit bin, which is workspace dependent and therefore prone to using unsupported lute versions. In general, however, it is a much better start